Trial experience get started #3951
Conversation
🔍 Preview links for changed docs |
Vale Linting ResultsSummary: 12 suggestions found 💡 Suggestions (12)
|
…s-content into trial-experience-get-started
|
@lcawl @jmikell821 Please have another look — thanks! |
lcawl
left a comment
lcawl
left a comment
There was a problem hiding this comment.
I think this is a great evolution over the previous content. Added some comments and questions...
Co-authored-by: Lisa Cawley <[email protected]>
shainaraskas
left a comment
shainaraskas
left a comment
There was a problem hiding this comment.
quickly hopped in with a couple of ideas
get-started/evaluate-elastic.md
Outdated
| - Consider adding complementary solutions (for example, Observability + Security). | ||
| - Expand data sources and integrations. | ||
| - Implement advanced features (ML, custom applications, APIs). |
There was a problem hiding this comment.
consider some helpful links here
There was a problem hiding this comment.
Any suggestion? I'd like to keep the list short
There was a problem hiding this comment.
just links on these bullet points so people can understand how do do these recommended actions
Co-authored-by: shainaraskas <[email protected]>
|
I moved the "Remove limitations" section of https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/create-an-organization out of the snippet, since it says you ought to do those subscription steps only after your trial is complete (and thus doesn't really fit in the flow of the new trial-specific page). I also moved it to a separate section in the original page, to align with the flow there as well (and enable other pages to link to it, if needed). I also combined the two bullet points about Elasticsearch serverless setting limitations (and added a link for more information). |
…s-content into trial-experience-get-started
Proposal to fix #3611. This is a fully experimental draft to explore ways of composing the requested content.
LLM usage disclosure: I fed the issues description from #3611 to Claude 4.5 Sonnet in Cursor, then reviewed the content manually and fixed Vale linting issues. I also ran the docs through the Elasticsearch experimental MCP server to check for consistency and accuracy.